Skip to content

fix: isolate and safely reap Chrome automation - #46

Open
ruby-dlee wants to merge 18 commits into
mainfrom
fm/chrome-leak-fix-k2
Open

fix: isolate and safely reap Chrome automation#46
ruby-dlee wants to merge 18 commits into
mainfrom
fm/chrome-leak-fix-k2

Conversation

@ruby-dlee

@ruby-dlee ruby-dlee commented Jul 28, 2026

Copy link
Copy Markdown
Owner

Intent

Publish the already-reviewed four-part Chrome automation safety fix while preserving the explicit reversion of all unrelated main-branch Behavior and Herdr CI fixes; leave PR 46 open and do not merge.

What Changed

  • Isolate each crew task’s Chrome automation in a dedicated browser profile and process group, with credential-safe launch flags and stable Chrome excluded from automation.
  • Reap task-owned browser processes during teardown, failed spawn rollback, and locked bootstrap orphan sweeps, while preserving unrelated and legacy browser processes by default.
  • Add lifecycle, routing, cleanup, and macOS smoke coverage plus browser isolation and verification documentation.

Testing

  • ⏭️ Test - skipped

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

⏭️ **Review** - skipped

Step was skipped.

⏭️ **Test** - skipped

Step was skipped.

⏭️ **Document** - skipped

Step was skipped.

⏭️ **Lint** - skipped

Step was skipped.

✅ **Push** - passed

✅ No issues found.

@ruby-dlee ruby-dlee changed the title fix: isolate and reap crew automation browsers fix(spawn): isolate and reap task automation browsers Jul 28, 2026
@ruby-dlee ruby-dlee changed the title fix(spawn): isolate and reap task automation browsers fix: isolate and safely reap Chrome automation Jul 28, 2026
@ruby-dlee
ruby-dlee force-pushed the fm/chrome-leak-fix-k2 branch from 2889914 to 48ac858 Compare July 29, 2026 02:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant